APPN Set Node

The APPN architecture allows four types of nodes in a network:

The device can be configured as an APPN network node that supports connections with all four node types. The device cannot function as an end node for APPN.

This option allows you to configure APPN node parameters.

Answer the following questions:

  1. Enable APPN

    This parameter enables or disables the router as an APPN network node.

    This parameter enables both APPN and HPR routing capability for this network node which consists of defining the Network ID and CP name for this node. APPN, however, must be enabled on the particular ports on which you desire to support APPN routing. Additionally, support for HPR must be enabled on the particular APPN ports desired and must be supported by the particular link stations on those ports.

    Valid Values: Yes, No

    Default Value: Yes

  2. Network ID (required)

    This parameter specifies the name of the APPN network to which this network node belongs. The network ID must be the same for all network nodes in the APPN network. Attached APPN end nodes and LEN end nodes can have different network IDs.

    Valid Values:

    A string of 1 to 8 characters:

    A network identifier for an existing network, of which this router network node is to become a member, using the special characters @, $, and # from the character set A, continues to be supported; however, these characters should not be used for new network IDs.

    Default Value: None

  3. Control point name (required)

    This parameter specifies the name of the CP for this APPN network node. The CP is responsible for managing the APPN network node and its resources. The CP name is the logical name of the APPN network node in the network. The CP name must be unique within the APPN network identified by the Network ID parameter.

    Valid Values:

    A string of 1 to 8 characters:

    An existing CP name that this node would be acquiring, using the special characters @, $, # from the character set A, continues to be supported; however, these characters should not be used for new CP names.

    Default Value: None

  4. Enable Branch Extender

    This parameter specifies whether the Branch Extender function will be enabled on this node. If yes is specified, the Branch Extender function will be enabled on this node. If no is specified, additional questions related to Branch Extender will not be asked during Node, Port, and Link Station definitions.

    Valid Values: Yes or No

    Default Value: No

  5. Permit search for unregistered LUs

    This parameter specifies whether this node (when acting as an End Node) can be searched for LUs even if the LUs were not registered with the network node server of the Branch Extender. If yes is specified, this node can be searched for LUs.

    Valid Values: Yes or No

    Default Value: No

  6. Route addition resistance

    This parameter indicates the desirability of routing through this node. This parameter is used in the class of service based route calculation. Lower values indicate higher levels of desirability.

    Valid Values: 0 to 255

    Default Value: 128

  7. XID number for subarea connection

    This parameter specifies a unique ID number (identifier) for the network node. The XID number is combined with an ID block number (which identifies a specific IBM product) to form an XID node identification. Node identifications are exchanged between adjacent nodes when the nodes are establishing a connection. The router network node automatically appends an ID block number to this parameter during the XID exchange to create an XID node identification.

    The ID number you assign to this node must be unique within the APPN network identified by Network ID parameter. Contact your network administrator to verify that the ID number is unique.

    Valid Values: A string of 5 hexadecimal digits

    Default Value: X'00000'

    Node identifications are normally exchanged between T2.1 nodes during CP-CP session establishment. If the network node is communicating with the IBM Virtual Telecommunications Access Method (VTAM) product through a T2.1 LEN node and the LEN node has a CP name defined for it, the XID number parameter is not required. If the adjacent LEN node is not a T2.1 node or does not have an explicitly defined CP name, the XID number parameter must be specified to establish a connection with the LEN node. VTAM versions prior to Version 3 Release 2 do not allow CP names to be defined for LEN nodes.

  8. Use enhanced BATCH COS

    This parameter specifies whether to use the enhanced COS tables. The enhanced tables assign reasonable weights to ATM TGs based on cost, speed, and delay. For ATM, the order of preference is:

    Valid Values: Yes or No

    Default Value: Yes

  9. Use enhanced BATCHSC COS

    This parameter specifies whether to use the enhanced COS tables. The enhanced tables assign reasonable weights to ATM TGs based on cost, speed, and delay. For ATM, the order of preference is:

    Valid Values: Yes or No

    Default Value: Yes

  10. Use enhanced INTER COS

    This parameter specifies whether to use the enhanced COS tables. The enhanced tables assign reasonable weights to ATM TGs based on cost, speed, and delay. For ATM, the order of preference is:

    Valid Values: Yes or No

    Default Value: Yes

  11. Use enhanced INTERSC COS

    This parameter specifies whether to use the enhanced COS tables. The enhanced tables assign reasonable weights to ATM TGs based on cost, speed, and delay. For ATM, the order of preference is:

    Valid Values: Yes or No

    Default Value: Yes

    Select the Submit button.